The original link is broken along with all the links on Vitalik's original website (vitalik.ca)

Attention (CC)

Summary of changes

Description of the changes included in this pull request.
Steps to follow to confirm the feature is completed or the bug/issue is resolved.
Are there any dependencies?
Does this code break any existing functionality or introduce any risk?

Relevant Context

• Feature: [ticket number](link to project management ticket)
• Relevant Pull Request: #

How Has This Been Tested?

Screenshots (if appropriate):

Further comments

Types of changes

• [ x] Content edit, File upload, content addition
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Technical Documentation Update
• Other (please describe):

Does this introduce a breaking change?

Breaking change is defined as "A fix or feature that would cause existing functionality to change."

• Yes
• [ x] No

Checklist:

• [ x] My code follows the code style of this project.
• I have added tests that prove my fix is effective or that my feature works
• I have added/changed necessary documentation (if appropriate)
• All new and existing tests passed.